feat: add bug-triage Claude skill#4109
Merged
Merged
Conversation
Adds a Claude skill that reads the project bug triage guide, classifies open requires-triage issues, and files a dated summary issue with recommended priority and area labels for a human to review and apply.
Reverses the earlier read-only behavior. The skill now applies the recommended priority and area labels and removes requires-triage; the dated summary issue records what was done so a human reviewer can spot-check and close it.
comphead
reviewed
Apr 27, 2026
| For each issue, review the title and body and determine: | ||
|
|
||
| 1. **Priority label** (exactly one): apply the decision tree from the guide. | ||
| - `priority:critical` if it could produce silent wrong results |
Contributor
There was a problem hiding this comment.
should we say correctness issues?
what about security issues?
comphead
reviewed
Apr 27, 2026
| 1. **Priority label** (exactly one): apply the decision tree from the guide. | ||
| - `priority:critical` if it could produce silent wrong results | ||
| - `priority:high` for crashes, panics, segfaults, NPEs on supported paths | ||
| - `priority:medium` for functional bugs / perf regressions with workarounds |
Contributor
There was a problem hiding this comment.
Suggested change
| - `priority:medium` for functional bugs / perf regressions with workarounds | |
| - `priority:medium` for functional bugs / performance regressions with workarounds |
Summary issue body now uses one subsection per priority, ordered highest first, with one bullet per issue (title plus linked number) and sub-bullets for area labels, good-first-issue flag, and rationale. Drops the markdown table form. Also folds in PR review feedback: priority:critical now explicitly covers correctness issues and security vulnerabilities, and "perf regressions" is spelled out as "performance regressions".
Member
Author
|
Thanks for review @comphead. I addressed feedback and made other improvements such as listing by priority, showing issue titles, using bullets instead of markdown table |
Member
Author
|
Latest triage issue created with this skill: |
coderfender
approved these changes
May 4, 2026
Contributor
coderfender
left a comment
coderfender
left a comment
There was a problem hiding this comment.
LGTM ! Perhaps we could keep fine tuning it based on the results / experience in the next few weeks ?
Member
Author
Absolutely. Once this one is merged, anyone can create PRs to improve as needed. Thanks for the approval @coderfender |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
We have a bug triage guide at
docs/source/contributor-guide/bug_triage.mdbut no automated way to work through the backlog of issues labeledrequires-triage. This adds a Claude skill that does the triage pass against the guide and produces an audit trail.What changes are included in this PR?
A new
.claude/skills/bug-triage/SKILL.mdthat:docs/source/contributor-guide/bug_triage.mdas the source of truth for priority, area labels, and escalation rulesrequires-triagegood first issue(where appropriate) and removesrequires-triagerequires-triageintact on them so they show up in the next passBug triage results: YYYY-MM-DD) recording every decision plus skipped and failed entries, for a human reviewer to spot-check and closeThe skill is explicit about what it must not do: no inventing labels, no commenting on triaged issues, no closing issues, no AI attribution in the summary.
How are these changes tested?
No automated tests. This is a Claude skill (markdown instructions); behavior is exercised by invoking the skill against the live
apache/datafusion-cometissue list. The summary issue created by each run is itself the human-reviewable artifact.